Selective presentation of real-time contact options based on user and system parameters

ABSTRACT

Embodiments for presenting real-time contact options described generally herein. The system receives information from a first user about an offered item via a web page and communication preferences for use with a real-time contact option to be presented on the web page, whereby the communication preferences including a first-user-defined real-time contact option presentation condition. The system selectively presents to a second user the information about the offered item and the real-time contact option based on a determination that the first-user-defined real-time contact option presentation condition is satisfied. The system enables the second user to select the real-time contact option. In response to the second user selecting the real-time contact option, the system communicates to the first user a real-time contact request and information identifying the second user.

PRIORITY

This application is a continuation of U.S. patent application Ser. No.15/626,932, filed Jun. 19, 2017, which claims the benefit of priority toU.S. patent application Ser. No. 11/508,091, entitled “SELECTIVEPRESENTATION OF REAL-TIME CONTACT OPTIONS BASED ON USER AND SYSTEMPARAMETERS,” filed on Aug. 22, 2006, which is hereby incorporated byreference herein in its entirety.

TECHNICAL FIELD

Various embodiments described herein relate generally to publicationserver systems (ES), including apparatus, systems, and methods used inproduct or service sales publication servers.

BACKGROUND INFORMATION

A publication server may act as an interface between one or more sellersoffering goods or services for purchase or bid. A seller may provideproduct or service information, pricing information, and contactinformation to a publication server via a seller interface. Thepublication server may generate an electronic representation of thesellers' product or service offering where a buyer may be able to viewthe representations via an electronic interface.

In order to expedite sales or inspire conference in a seller's productor service, a publication server may enable a potential buyer to requestadditional information about a seller's representation or listing viathe buyer interface.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of product or service publication serverarchitecture according to various embodiments.

FIG. 2 is a diagram of communication between a buyer device, publicationdevice, and seller device in a product or service publication serverarchitecture according to various embodiments.

FIG. 3 is a block diagram of product or service publication serveraccording to various embodiments.

FIG. 4 is a flow diagram illustrating several methods according tovarious embodiments.

FIG. 5 is a flow diagram illustrating several methods according tovarious embodiments.

FIG. 6 is a flow diagram illustrating several methods according tovarious embodiments.

FIG. 7 is a flow diagram illustrating several methods according tovarious embodiments.

FIG. 8 is a block diagram of an article according to variousembodiments.

FIG. 9 is a block diagram of an article according to variousembodiments.

DETAILED DESCRIPTION

FIG. 1 is a block diagram of a product or service publication serverarchitecture 10 comprising a buyer device (BD) 42, publication device(PD) 22, and seller device (SD) 32, according to various embodiments.The buyer device 42 may be coupled to the publication device 22 via anetwork 14 where the network may be a local wired or wireless network ora network of networks such as the Internet. The seller device 32 mayalso be coupled to the publication device 22 via the network 14 wherethe network may be a local wired or wireless network or a network ofnetworks such as the Internet. The seller device 32 may be part of thepublication device 22 where the publisher is also the seller.

The publication device 22 includes a server 24 where the server 24 maybe configured to communicate messages between the buyer device 42 andthe publication device 22. The server 24 may also be configured tocommunicate messages between the publication device 22 and the sellerdevice 32. The seller device 32 may have an interface 34 that may beconfigured to communicate messages between the publication device 22 anditself. In an embodiment, a buyer device 42 may have an interface 44that may be configured to communicate messages between the publicationdevice 22 and itself. The interfaces 34 and 44 may each include ahyper-text markup language (HTML) converter such as a browser and theserver 24 may communicate messages between the publication device 22 andbuyer device 42 and seller device 32 via one or more web pages.

The architecture 10 may include a voice communication provider (VCP) 52that is coupled to the network 14. The voice communication provider 52may include a Voice over Internet Protocol (VoIP) server 54. Thepublication device 22 may enable the voice communication provider 52 toestablish voice communication between the buyer device 42 and sellerdevice 32. The voice communication provider 52 may establish VoIPcommunication between the seller device 32 and buyer device 42. Theinterface 44 or interface 34 may be able to establish VoIP sessions viaa browser, a thin client, or a VoIP application specific program (ASP).The publication device 22 server 24 may include a VoIP server.

The publication device 22 may establish VoIP communication between aseller device 32 and buyer device 42 by providing peer-to-peerconnection information for both devices 32, 42. The seller device 32 andbuyer device 42 may form a peer-to-peer connection that enables voice orother real-time communication between the devices 32, 42. The sellerdevice 32 and buyer device 42 may act as effective client and servers inpeer-to-peer connections and may be responsible for terminating suchsessions via peer-to-peer software or protocols. The seller device 32and buyer device 42 may host a communication client to supportpeer-to-peer connections and an access client for browser basedcommunication.

The architecture 10 may also include plain-old-telephone-system (POTS)12 coupled to the voice communication provider 52. In an embodiment aseller may have one or more phones 36 coupled to the POTS 12 (includingcellular phones). The seller device 32 may specify one or more phonenumbers associated with the seller phone(s) 36 where publication device22 initiated voice communication may be to be directed. In an embodimenta buyer may have one or more phones 46 coupled to the POTS 12 (includingcellular phones). The buyer device 42 may specify one or more phonenumbers associated with the buyer phone(s) 46 where publication device22 initiated voice communication may to be directed. The publicationdevice 22 may employ the voice communication provider 52 to establishcommunication between any combination of a buyer device 42, a sellerdevice 32, a seller phone 36, and buyer phone 46.

The buyer device 42 may be any computer device capable of providing aninterface 44 including a computer, personal data assistant, or webenabled cellular phone. The buyer device 42 may be able to establishVoIP sessions including peer-to-peer sessions via a client or receivecalls via a telephone number. The seller device 32 may be any computerdevice capable of providing an interface 34 including a computer,personal data assistant, or web enabled cellular phone. The buyer device42 may be able to establish VoIP sessions or receive calls via atelephone number.

FIG. 2 is a diagram of communications 40 between a publication device 22and a buyer device 42 and between the publication device 32 and a sellerdevice 32 according to various embodiments. In an embodiment, a sellermay have products or services for sale or bid. The seller via a sellerdevice 32 may engage a publication device 22 to generate an electroniccatalog or listing(s) of the sellers' products or services for sale orbid. A buyer via a buyer device 42 may view the electronic catalog orlisting(s) and purchase, offer to purchase, or bid on one or moreproducts or services shown in the electronic catalog or listing(s). Inan embodiment a seller via a seller device 32 may register or setup anaccount or services with the publication device 22. A seller via aseller device 32 may generate a seller general setup request 62. In anembodiment a seller may employ the interface 34 to generate the request62 via a web page provided by the publication device 22 server 24.

In response to the seller general setup request 62, the publicationdevice 22 may generate a seller general setup page 64 and provide it tothe seller device 32 as an HTML document, may for example.. The setuppage 64 may enable a seller to set numerous preferences, accountinformation, and contact information. In an embodiment, the preferencesmay include the ability of a buyer or potential buyer to contact theseller via real-time communication. The real-time communicationpreferences may include the seller's availability schedule (based on theseller's time zone), the seller's spoken and written languages, seller'sdesire to have an interpreter participate in a voice or text call forcertain other languages, one or more contact numbers or VoIP identifiersto be used according to a schedule or product or service. The real-timecommunication preferences may also include a list of buyers (byidentifier or other unique reference) that are excluded or permitted tocommunicate with the seller via voice communication, required relatedproduct or service sale status including requirements that a buyer hasoffered to buy, purchased, bid, or placed a bid meeting a predeterminedminimum or reserve, or has a certain buyer history or rating asestablished by the publication device 22 server 24.

The seller device 32 may forward the seller general setup reply 66 tothe publication device 22 server 24. In an embodiment, the publicationdevice 22 may store the seller information and preferences in one ormore databases. A potential buyer or buyer via a buyer device 42 maygenerate a buyer general setup request 92. A buyer or potential buyermay employ the interface 44 to generate the request 92 via a web pageprovided by the publication device 22 server 24. A buyer device 42 maybe able to communicate with the publication device 22 withoutregistration or unique identification. In another embodiment, a buyervia a buyer device 42 may have the option of registering or providing aunique identifier when communicating with the publication device 22.

In response to the buyer general setup request 92, the publicationdevice 22 may generate a buyer general setup page 94 and provide it tothe buyer device 42 as an HTML document. The buyer general setup page 94may enable a potential buyer to set numerous preferences, accountinformation, and contact information. The preferences may includereal-time communication preferences. In an embodiment, buyer real-timecommunication preferences may include the buyer's availability schedule(for receipt of seller's communication requests to the buyer), thebuyer's spoken or written languages, buyer's desire to have aninterpreter participate in a voice or text calls for certain otherlanguages, one or more contact numbers or VoIP identifiers to be usedaccording to a schedule or product or service. The real-timecommunication preferences may also include a list of sellers (byidentifier or other unique reference) that are excluded or permitted tocommunicate with the buyer via voice communication, required relatedproduct or service sale status including whether the buyer has offeredto buy, purchased, bid, or placed a bid meeting a predetermined minimumor reserve, and the seller's history or rating as established by thepublication device 22 server 24.

The buyer device 42 may forward the buyer general setup reply 96 to thepublication device 22 server 24. In an embodiment, the publicationdevice 22 may store the buyer information and preferences in one or moredatabases. A seller via a seller device 32 may create a catalog orlisting of one or more products or services offerings (items in anembodiment) by generating a sell item request 72. In an embodiment aseller may select an option to generate a sell item request 72 via aseller device 32 from a web page generated by the publication device 22.A seller may receive a sell item page 74 from the publication device 22server 24 and populate the page via the seller device 32 interface 34.The seller may be able to specify item information includingdescription, reserve, multimedia (including pictures, or videos), linksto other information or multimedia, and buyer real-time contactpreferences for the particular listing.

Upon completion of the sell item page 74, a seller via the seller device32 interface 34 may forward the completed page 74 via a sell item pagereply 76. A buyer via a buyer device 42 interface 44 may generate a viewitem request 102. The buyer via a buyer device 42 interface 44 mayperform a search for items (e.g., products or services offered) using anumber of criteria including item description, multimedia matching, itemgeographical location, particular seller, ability to potentially contactseller via real-time communication with questions about an item, orpricing. The view item request 102 may be generated by a buyer selectingan item located in a search in an embodiment. The publication device 22server 24 may generate a view item page 104 for the view item request102 and forward the view item page 104 to the buyer via the buyer device42 interface 44. The publication device 22 server 24 may retrieveinformation about the requested item from one or more databases whencompiling a view item page 104. The view item page 104 may include areal-time contact icon (or some other user-selectable indicia) that abuyer may select via the buyer device 42 interface 44 to contact aseller via a real-time communication method, apparatus, or protocolincluding via voice, instant message, or other instant contact method orapparatus.

The publication device 22 may apply general rules, seller preferences,and buyer preferences to determine what, if any, contact icons may beincluded on the view item page 104 where the general rules, sellerpreferences, and buyer preferences may be stored in one or moredatabases accessible by the server 24. The publication device 22 server24 may apply general rules for buyer-seller real-time communicationsincluding the number of real-time communications sessions conducted orattempted by a buyer or seller in a predetermined time period via thepublication device 22, geographical attributes of the buyer or seller,the number of buyers already shown a contact icon for the seller andlikelihood of one or more such buyers to attempt to contact the sellervia the real-time contact icon, or unique identification of buyer (e.g.,buyer logged into the publication device 22 server 24 in an embodiment).

A buyer receiving a view item page 104 with a seller real-time contactoption (SRO) may select the real-time contact option icon and generatean item real-time contact request 112. The publication device 22 server24 upon detecting the real-time contact option icon selection or receiptof the item real-time contact request may generate a real-time contactrequest page 82 for the seller device 32. The seller real-time contactrequest 82 may include an icon (or some other user-selectable indicia)for accepting the buyer real-time contact request. The page 82 mayinclude a unique buyer identifier, information about the item(s) shownon the view item page 104 including description, item sales status ingeneral and particular to the buyer, past interactions with the buyerincluding sales, contacts, or buyer language(s). The item sales statusmay include the number of items in inventory, number of orders inpredetermined time frame, offers, offers exceeding a preset reserve,buyer's current offer for item (if any).

In an embodiment, a seller via a seller device 32 interface 34 mayaccept a real-time communication request 82 by selecting an acceptanceicon on a web page presenting the real-time communication request 82.The seller via a seller device 32 interface 34 may decline a real-timecommunication request 82 by selecting a declination icon on a web pagepresenting the real-time communication request 82. If a seller acceptsor declines the request 82, the seller device 32 interface 34 maygenerate a real-time contact reply 84. The publication device 22 server24 upon receipt of the real-time contact reply 84 (e.g., selection ofthe acceptance or declination icon on a web page in an embodiment) maygenerate an item real-time contact reply 114 and forward the reply 114to a buyer device 42 interface 44. The publication device 22 maygenerate a declination reply if a seller via a seller device 32interface 34 does not respond within a predetermined time period. Thepublication device 22 server may store the real-time communicationrequests and responses in one or more databases.

When a seller via a seller device 32 interface 34 accepts a real-timecommunication request 82, the publication device 22 server 24 mayinitiate or request initiation of the requested real-time communication.In an embodiment, when the real-time communication request is a voicecommunication request, the publication device 22 server 24 may forwardcontact information for the buyer and seller to a voice communicationprovider 52. The voice communication provider 22 may attempt to initiatethe requested communication based on the received contact information.In an embodiment, the voice communication provider server 54 may createa VoIP session between one of a buyer device 42 and buyer phone 46 andone of a seller device 32 and seller phone 36. The voice communicationprovider 52 may forward voice communication to a POTS 12 forcommunication with a buyer phone 46 or seller phone 36. The provider 52may provide connection information to the seller device 32 and buyerdevice 42 that enables communication clients in each device 32, 42 toestablish peer-to-peer voice communication. The voice communicationprovider 52 server 54 may be a VoIP provider such as Skype™ or mayemploy a VoIP provider such as Skype™ to form VoIP sessions. The sellerdevice 32 and buyer device 42 may employ Skype™ clients to enablepeer-to-peer voice communication based on connection informationprovided by the publication device 22 or VCP 54.

The publication device 22 server 24 may determine contact informationfor the buyer and seller based on their communication preferences,including VoIP unique identifiers or telephone number(s) for the buyerand seller for voice communication sessions. The publication device 22server 24 may provide the buyer's and seller's VoIP unique identifiers(for peer-to-peer sessions in an embodiment) or telephone number(s) tothe voice communication provider 52 for voice communication requests. Abuyer or seller may be able to end a communication session via a buyerdevice 42 interface 44, a buyer phone 46, a seller device 32 interface34, or a seller phone 36. The publication device 22 server 24 may limitcommunication sessions to a predetermined time period.

In an embodiment, the publication device 22 server 24 may include anumber of modules such as shown in FIG. 3 including a buyer generalsetup module 122, general contact module 124, view item module 126,seller general setup module 128, buyer contact module 132, seller—sellitem module 134, seller contact module 136, and seller—revise itemmodule 138. In an embodiment, the buyer general setup module 122 mayenable a buyer via a buyer device 42 interface 44 to configure or modifygeneral buyer information including buyer contact information includingvoice contact information. The module 122 may process buyer generalsetup requests 92 and replies 96 and generate buyer general setup pages94. In an embodiment, the seller general setup module 128 may enable aseller via a seller device 32 interface 34 to configure or modifygeneral seller information including seller contact informationincluding voice contact information. The module 128 may process sellergeneral setup requests 62 and replies 66 and generate seller generalsetup pages 64.

The general contact module 124 may enable an agent or agentadministrator to configure or modify general contact rules includingvoice session rules related to buyers and sellers. In an embodiment, theview item module 126 may enable a buyer via a buyer device 42 interface44 to view requested item information including potential real-timeseller contact options. The view item module 126 may process view itemrequests 102 and generate view item pages 104. The seller-sell itemmodule 134 may enable a seller via a seller device 32 interface 34 toconfigure information for items for sale or bid including potentialreal-time seller contact options. The seller-sell item module 134 mayprocess sell item requests 72 and replies 76 and generate sell itempages 74.

In an embodiment, the seller revise item module 138 may enable a sellervia a seller device 32 interface 34 to revise or modify item informationincluding real-time seller contact options. The buyer contact module 132may enable a buyer via a buyer device 42 interface 44 to request or endreal-time communication with a seller. The buyer contact module 132 mayprocess item real-time contact requests 112 and generate item real-timereplies 114. In an embodiment, the seller contact module 136 may enablea seller via a seller device 32 interface 34 to reply to real-timecommunication requests or end real-time communication with a buyer. Theseller contact module 136 may process item real-time contact replies 82and generate item real-time requests 84.

FIG. 4 is a flow diagram of a seller real-time-contact option activationmethod 150 according to various embodiments. The method 150 may applygeneral contact rules to determine whether any general rule is flaggedor may be violated by presenting a real-time contact option on a viewitem page requested by a buyer via a buyer device 42 interface 44(activity 152). When a general rule is flagged (due to the itemrequested, buyer (if known), or seller), a real-time contact option maynot be presented on a view item page in an embodiment (activity 154). Inan embodiment, the method 150 may apply seller contact rules todetermine whether any seller rule is flagged or may be violated bypresenting a real-time contact option on a view item page requested by abuyer via a buyer device 42 interface 44 (activity 156).

When a seller rule is flagged (due to the item requested, or buyer (ifknown)), a real-time contact option on a view item page may not bedisplayed in an embodiment (activity 158). In an embodiment, when thegeneral contact rules and the seller contact rules have been cleared(e.g., no flag(s) set or rule potentially violated by possiblepresentation of a seller real-time contact option), the method 150 mayenable real-time contact option presentation on a buyer view item page(VIP) (activity 162). A view item page may present a sellerreal-time-contact option for different real-time communication methods,apparatus, or protocols including voice, instant message, or otherinstant contact method, apparatus, or protocol. The method 150 may beemployed to separately determine whether to present a real-time-contactoption for each seller real-time-contact option where each option mayhave different general rules or seller rules.

FIG. 5 is a flow diagram of a general contact rule evaluation method 190according to various embodiments. In the general contact rule evaluationmethod 190, a number of general contact rules may be evaluated todetermine whether a real-time contact option should be presented to abuyer. In an embodiment, the method 190 may determine whether a buyer(to possibly be shown a seller real-time contact option) is currentlylogged into the publication device 22 via the buyer device 42. In anembodiment a buyer may remain logged into a publication device 22 viabuyer device 42 for a predetermined time interval. In anotherembodiment, the publication device 22 may determine whether a uniquebuyer is known based on the buyer device 32 coupled to the publicationdevice 22 (such as via a cookie in some Internet browser applications).In an embodiment, when a buyer is not logged into the publication device22 or cannot be uniquely identified (activity 192), the method 190 mayset a general contact rule flag (activity 202).

In an embodiment, the method 190 may determine whether the buyer topossibly be shown a real-time contact option has exceeded apredetermined number of real-time contacts (activity 194) in apredetermined time interval. The predetermined number may vary as afunction the real-time contact type, e.g., voice or instant message. Thepredetermined time interval may also be based on a calendar day, week,month, year, or some other predetermined time interval. In anembodiment, when a buyer has exceeded a predetermined number ofreal-time contacts within a predetermined time interval (activity 194),the method 190 may set a general contact rule flag (activity 202).

In an embodiment, the method 190 may determine whether any geographicalor demographical issues may exist between the buyer and seller. Thepublication device 22 may employ a number of servers 24 where theservers 24 are geographical based such as for different countries orcontinents. The method 190 may limit potential voice sessions to buyersand sellers on the same server, within the same country or continent. Inan embodiment, the method 190 may determine whether the item to beviewed by a buyer has potential export issues (to the buyer country orfrom the seller country). If export issues potentially exist,geographical issues exist, or demographical issues exist, the method 190may set a general contact rule flag (activity 202).

In an embodiment, the method 190 may determine the number of buyerdevices 42 actively viewing an item page that includes a real-timecontact option icon (activity 198). When the buyer device activereal-time contact option icon count number exceeds a predetermined limitincluding a maximum system limit, a seller limit, and a specific itemlimit, the method 190 may set a general contact rule flag (activity202). The publication device 22 may employ a database or queue tomonitor each real-time contact option currently shown on an item page.The method 190 may accumulate totals for the system (publication device22), specific seller(s), or specific items. The method 190 may thendetermine whether to present an real-time contact option for a specificitem based on the accumulated totals. The predetermined real-timecontact option limit may be set as a function of past system activity,seller activity, item activity, probably of buyer(s) selecting a shownreal-time contact option icon, and other related statistics.

FIG. 6 is a flow diagram of a seller contact rule evaluation method 210according to various embodiments. In the seller contact rule evaluationmethod 210, a number of seller specific contact rules may be evaluatedto determine whether a seller real-time contact option (seller real-timecontact option) should be presented to a buyer. In an embodiment, aseller via a seller device 32 may set a number of real-time contactoption rules via a seller general setup page 64 (FIG. 2). A seller mayselect or deselect real-time contact option rules and set associatedparameters via the general setup page 64. A seller via a seller device32 interface 34 may select or deselect item specific real-time contactoption rules and set associated parameters via a sell item page 74.

In an embodiment, the method 210 may determine whether item specificrequirements or rules (if any) have been met or satisfied (activity212). When an item specific requirement or rule has not been met, themethod 210 may set a seller contact rule flag (activity 222). The itemspecific rules may include the item sales status or item sales value.The method 210 may determine whether the buyer associated with the buyerdevice 42 has been flagged by the seller via the seller device 32(activity 214). When a buyer associated with the buyer device 42 hasbeen flagged by a seller via the seller device 32, the method 210 mayset a seller contact rule flag (activity 222). A seller via the sellergeneral setup page 64 may create a list of buyers that are permitted ornot permitted to have real-time contact with the seller. The buyerexclude/include real-time contact option list may be maintained by thepublication device 22 server 24.

The method 210 may determine whether buyer specific requirements orrules (if any) have been met or satisfied (activity 216). When a buyerspecific requirement or rule has not been met, the method 210 may set aseller contact rule flag (activity 222). The buyer specific requirementsor rules may include a certain level of buyer experience with one of apublication device 22 and the seller associated with the item page beingrequested. In an embodiment, the method 210 may determine whether therequested item page is to be shown within a seller's predefinedreal-time-contact schedule (activity 218). When the requested item pageis to be shown outside the associated seller predefinedreal-time-contact schedule, the method 210 may set a seller contact ruleflag (activity 222). In an embodiment, a seller may set a generalreal-time contact schedule or a real-time contact schedule specific tothe item to be shown on the view item page.

FIG. 7 is a flow diagram of a buyer item real-time contact requestmethod 170 according to various embodiments. In an embodiment, when abuyer via a buyer device 42 interface 44 selects a real-time contactoption on an item page (activity 172), the method 170 may determinewhether the seller device 32 interface 34 is active (seller online)(activity 174). In an embodiment, when the method 170 determines aseller is not online, the method 170 may determine whether the seller isaccepting the requested real-time contact option offline (activity 176).The seller via a seller general setup page 64 or sell item page 74 (orrevise item page), may specify one or more rules for variousreal-time-contact options. In an embodiment, when the requestedreal-time contact option is for voice contact, a seller may specify oneor more telephone numbers to used to establish voice communication whenthe seller is offline or online.

When the seller has specified an offline setup for the selected sellerreal-time contact option, the method 170 may enable the selectedreal-time contact option via the seller specified setup (activity 186).The seller via a seller device 32 may specify message options when theseller is offline or does not answer or accept a seller real-timecontact option. When the seller has not specified an offline setup forthe selected real-time contact option or has elected not to accept theselected real-time contact option offline, the method 170 may give thebuyer (via the buyer device 32 or buyer device telephone 36) a messageoption (activity 188) specified by a seller for such an real-timecontact option request.

When the seller is online (seller device 32 interface 34 is active), themethod 170 may generate a real-time contact request page (RRP) 82(activity 178). In an embodiment, the real-time contact request page 82may include information about the buyer and item associated with theselected contact option. The buyer information may include a uniquebuyer identifier, history of past contact attempts by the buyer, historyof past sales between the buyer and seller, buyer bid or purchase statusfor the related item, and buyer general saleshistory/rating/creditability. The item information may include the itembid or sales status, unique item identifier, item description, and itemmultimedia (including pictures or video). The method 170 may forward thebuyer information page (in the RRP 82 in an embodiment) to the seller'sseller device 32 interface 34 (activity 184).

In an embodiment, when the seller via a seller device 32 accepts therequested seller real-time contact option, the method 170 may enable therequested real-time contact option (activities 184, 186). The method 170may engage the publication device 22 server 24 or a voice communicationprovider 52 to enable or request enablement of the requested andaccepted seller real-time contact option. In an embodiment, when theseller via a seller device 32 does not accept the requested sellerreal-time contact option, the method 170 may give the buyer (via thebuyer device 32 or buyer device telephone 36) a message option specifiedby a seller for such an real-time contact option request (activities184, 188).

A device 260 is shown in FIG. 8 that may be used in various embodimentsas a buyer device 42 or seller device 32. The device 60 may include acentral processing unit (CPU) 262, a random access memory (RAM) 264, aread only memory (ROM″) 266, a display 268, a user input device 272, atransceiver application specific integrated circuit (ASIC) 274, amicrophone 288, a speaker 282, and an antenna 284. The CPU 262 mayinclude a VoIP client 294 and a publication device 22 messageinterpreter 292. The RAM 264 may include a queue 278 where the queue 278may store publication device 22 messages. The interpreter 292 and theVoIP client 294 may be separate elements. The VoIP client 294 may enableVoIP sessions between a VoIP server and itself, or between another VoIPclient and itself. The interpreter 292 may process messages or pagesfrom and generate messages or pages for the publication device 22 server24.

The ROM 266 is coupled to the CPU 262 and may store the programinstructions to be executed by the CPU 262, VoIP client 294, andinterpreter 292. The RAM 264 is coupled to the CPU 262 and may storetemporary program data, overhead information, and the queues 278. Theuser input device 272 may comprise an input device such as a keypad,touch pad screen, track ball or other similar input device that allowsthe user to navigate through menus in order to operate the device 260.The display 268 may be an output device such as a CRT, LCD or othersimilar screen display that enables the user to read, view, or hearreceived messages or pages from the publication device 22 server 24.

The microphone 288 and speaker 282 may be incorporated into the device260. The microphone 288 and speaker 282 may also be separated from thedevice 260. Received data may be transmitted to the CPU 262 via a serialbus 276 where the data may include messages or pages received, messagesor pages to be transmitted, or protocol information. The transceiverASIC 274 may include an instruction set necessary to communicatemessages or pages in architecture 10. The ASIC 274 may be coupled to theantenna 284 to communicate wireless messages or pages within thearchitecture 10. When a message is received by the transceiver ASIC 274,its corresponding data may be transferred to the CPU 262 via the serialbus 276. The data can include wireless protocol, overhead information,and pages to be processed by the device 260 in accordance with themethods described herein.

FIG. 9 illustrates a block diagram of a device 230 that may be employedas a publication device 22 in various embodiments. The device 230 mayinclude a CPU 232, a RAM 234, a ROM 236, a storage unit 238, amodem/transceiver 244, and an antenna 246. The CPU 232 may include aVoIP server 254 and a server 252. The RAM 234 may include a queue ordatabase 248 where the queue 248 may be used to store buyer or sellerinformation including general information, contact configuration, saleshistory, and item information. The storage 238 may also include a queueor database 256 where the queue 256 may be used to store may be used tostore buyer or seller information including general information, contactconfiguration, sales history, and item information. The VoIP server 254and the server 252 may be separate elements.

In an embodiment, the VoIP server 254 may initiate and maintain VoIPsessions between a buyer device 42 or a buyer telephone 46 and a sellerdevice 32 or a seller telephone 36. In an embodiment, the VoIP server254 may be maintained and operated a third party VoIP provider includingSkype™. In an embodiment, the server 252 may be a publication server 24including the modules shown in FIG. 3.

The modem/transceiver 244 may couple, in a well-known manner, the device230 to the network 14 or POTS to enable communication with the sellerdevice 32, buyer device 42, and voice communication provider 52. In anembodiment, the modem/transceiver 244 may be a wireless modem or othercommunication device that may enable communication with the sellerdevice 32, buyer device 42, or voice communication provider 52. The CPU232 via the server 252 may direct communication between modem 244 andthe seller device 32, buyer device 42, or voice communication provider52.

The ROM 236 may store program instructions to be executed by the CPU232, VoIP server 254, or server 252. The RAM 234 may be used to storetemporary program information, queues, databases, and overheadinformation. The storage device 238 may comprise any convenient form ofdata storage and may be used to store temporary program information,queues, databases, and overhead information.

Any of the components previously described can be implemented in anumber of ways, including embodiments in software. Any of the componentspreviously described can be implemented in a number of ways, includingembodiments in software. Thus, the CPU 232, VoIP server 254, server 252,modem/transceiver 2444, antenna 246, storage 238, RAM 234, ROM 236,queue 248, queue 256, CPU 262, interpreter 292, VoIP client 294,transceiver ASIC 274, antenna 284, microphone 288, speaker 282, ROM 266,RAM 264, queue 278, user input 272, display 268, publication device 22,seller device 32, buyer device 42, and voice communication provider 52may all be characterized as “modules” herein.

The modules may include hardware circuitry, single or multi-processorcircuits, memory circuits, software program modules and objects,firmware, and combinations thereof, as desired by the architect of thearchitecture 10 and as appropriate for particular implementations ofvarious embodiments.

The apparatus and systems of various embodiments may be useful inapplications other than a sales architecture configuration. They are notintended to serve as a complete description of all the elements andfeatures of apparatus and systems that might make use of the structuresdescribed herein.

Applications that may include the novel apparatus and systems of variousembodiments include electronic circuitry used in high-speed computers,communication and signal processing circuitry, modems, single ormulti-processor modules, single or multiple embedded processors, dataswitches, and application-specific modules, including multilayer,multi-chip modules. Such apparatus and systems may further be includedas sub-components within a variety of electronic systems, such astelevisions, cellular telephones, personal computers (e.g., laptopcomputers, desktop computers, handheld computers, tablet computers,etc.), workstations, radios, video players, audio players (e.g., mp3players), vehicles, medical devices (e.g., heart monitor, blood pressuremonitor, etc.) and others. Some embodiments may include a number ofmethods.

It may be possible to execute the activities described herein in anorder other than the order described. Various activities described withrespect to the methods identified herein can be executed in repetitive,serial, or parallel fashion.

A software program may be launched from a computer-readable medium in acomputer-based system to execute functions defined in the softwareprogram. Various programming languages may be employed to createsoftware programs designed to implement and perform the methodsdisclosed herein. The programs may be structured in an object-orientatedformat using an object-oriented language such as Java or C++.Alternatively, the programs may be structured in a procedure-orientatedformat using a procedural language, such as assembly or C. The softwarecomponents may communicate using a number of mechanisms well known tothose skilled in the art, such as application program interfaces orinter-process communication techniques, including remote procedurecalls. The teachings of various embodiments are not limited to anyparticular programming language or environment.

The accompanying drawings that form a part hereof show, by way ofillustration and not of limitation, specific embodiments in which thesubject matter may be practiced. The embodiments illustrated aredescribed in sufficient detail to enable those skilled in the art topractice the teachings disclosed herein. Other embodiments may beutilized and derived therefrom, such that structural and logicalsubstitutions and changes may be made without departing from the scopeof this disclosure. This Detailed Description, therefore, is not to betaken in a limiting sense, and the scope of various embodiments isdefined only by the appended claims, along with the full range ofequivalents to which such claims are entitled.

Such embodiments of the inventive subject matter may be referred toherein individually or collectively by the term “invention” merely forconvenience and without intending to voluntarily limit the scope of thisapplication to any single invention or inventive concept, if more thanone is in fact disclosed. Thus, although specific embodiments have beenillustrated and described herein, any arrangement calculated to achievethe same purpose may be substituted for the specific embodiments shown.This disclosure is intended to cover any and all adaptations orvariations of various embodiments. Combinations of the aboveembodiments, and other embodiments not specifically described herein,will be apparent to those of skill in the art upon reviewing the abovedescription.

The Abstract of the Disclosure is provided to comply with 37 C.F.R. §1.72(b), requiring an abstract that will allow the reader to quicklyascertain the nature of the technical disclosure. It is submitted withthe understanding that it will not be used to interpret or limit thescope or meaning of the claims. In the foregoing Detailed Description,various features are grouped together in a single embodiment for thepurpose of streamlining the disclosure. This method of disclosure is notto be interpreted to require more features than are expressly recited ineach claim. Rather, inventive subject matter may be found in less thanall features of a single disclosed embodiment. Thus the following claimsare hereby incorporated into the Detailed Description, with each claimstanding on its own as a separate embodiment.

What is claimed is:
 1. A method comprising: causing, by a hardwareprocessor of a publication device, presentation of a view item web pageon a device of a first user, the view item web page comprisinginformation about an item and a real-time contact icon representing areal-time contact option to contact a second user; receiving, by thepublication device, an indication of a selection, by the first user, ofthe real-time contact icon; in response to receiving the indication ofthe selection, determining, by the publication system, whether a deviceinterface of the second user is active; based on the device interface ofthe second user being active, generating, by the publication system, areal-time contact request page that includes a contact request, a uniqueidentifier of the first user, and information about the item; andtransmitting, by the publication device to a device of the second user,the real-time contact request page.
 2. The method of claim 1, furthercomprising, based on the device interface of the second user not beingactive, determining whether the second user is accepting a real-timecontact option offline.
 3. The method of claim 1, wherein the real-timecontact request page further includes a history of past interactionsbetween the first user and the second user.
 4. The method of claim 1,further comprising: receiving an indication of acceptance of the contactrequest of the real-time contact request page; and based on aVoice-over-Internet Protocol (VoIP) communication option being selected,causing a VoIP session between the device of the first user and thedevice of the second user.
 5. The method of claim 1, further comprising,in response to not receiving a response to the contact request of thereal-time contact request page within a predetermined time period,generating a declination reply for transmission to the device of thefirst user.
 6. The method of claim 1, further comprising, prior topresenting the view item web page comprising the real-time contact iconrepresenting the real-time contact option, determining that no rule isflagged or violated by presenting the real-time contact option.
 7. Themethod of claim 1, further comprising, prior to presenting the view itemweb page comprising the real-time contact icon representing thereal-time contact option, verifying that the first user is on a list ofusers permitted to have real-time contact with the second user or thefirst user is not on a list of users not permitted to have real-timecontact with the second user.
 8. The method of claim 1, furthercomprising, prior to presenting the view item web page comprising thereal-time contact icon representing the real-time contact option,determining that the view item web page is being shown within apredefined real-time contact schedule of the second user, the real-timecontact icon being presented in response to the view item web page beingshown within the predefined real-time contact schedule.
 9. The method ofclaim 1, further comprising: causing presentation of a setup page to thesecond user; and receiving one or more preferences or conditions, viathe setup page, that indicate when the real-time contact option can beincluded on the view item web page.
 10. A publication device comprising:one or more hardware processors; and a storage medium storinginstructions that, when executed by the one or more hardware processors,cause the one or more hardware processors to perform operationscomprising: causing presentation of a view item web page on a device ofa first user, the view item web page comprising information about anitem and a real-time contact icon representing a real-time contactoption to contact a second user; receiving an indication of a selection,by the first user, of the real-time contact icon; in response toreceiving the indication of the selection, determining whether a deviceinterface of the second user is active; based on the device interface ofthe second user being active, generating a real-time contact requestpage that includes a contact request, a unique identifier of the firstuser, and information about the item; and transmitting, to a device ofthe second user, the real-time contact request page.
 11. The publicationdevice of claim 10, wherein the operations further comprise, based onthe device interface of the second user not being active, determiningwhether the second user is accepting a real-time contact option offline.12. The publication device of claim 10, wherein the real-time contactrequest page further includes a history of past interactions between thefirst user and the second user.
 13. The publication device of claim 10,wherein the operations further comprise: receiving an indication ofacceptance of the contact request of the real-time contact request page;and based on a Voice-over-Internet Protocol (VoIP) communication optionbeing selected, causing a VoIP session between a device of the firstuser and the device of the second user.
 14. The publication device ofclaim 10, wherein the operations further comprise, in response to notreceiving a response to the contact request of the real-time contactrequest page within a predetermined time period, generating adeclination reply for transmission to the device of the first user. 15.The publication device of claim 10, wherein the operations furthercomprise, prior to presenting the view item web page comprising thereal-time contact icon representing the real-time contact option,determining that no rule is flagged or violated by presenting thereal-time contact option.
 16. The publication device of claim 10,wherein the operations further comprise, prior to presenting the viewitem web page comprising the real-time contact icon representing thereal-time contact option, verifying that the first user is on a list ofusers permitted to have real-time contact with the second user or thefirst user is not on a list of users not permitted to have real-timecontact with the second user.
 17. The publication device of claim 10,wherein the operations further comprise, prior to presenting the viewitem web page comprising the real-time contact icon representing thereal-time contact option, determining that the view item web page isbeing shown within a predefined real-time contact schedule of the seconduser, the real-time contact icon being presented in response to the viewitem web page being shown within the predefined real-time contactschedule.
 18. The publication device of claim 10, wherein the operationsfurther comprise: causing presentation of a setup page to the seconduser; and receiving one or more preferences or conditions, via the setuppage, that indicate when the real-time contact option can be included onthe view item web page.
 19. A non-transitory machine-readable mediumcomprising instructions, which when executed by one or more processors,cause the one or more processors to perform operations comprising:causing presentation of a view item web page on a device of a firstuser, the view item web page comprising information about an item and areal-time contact icon representing a real-time contact option tocontact a second user; receiving an indication of a selection, by thefirst user, of the real-time contact icon; in response to receiving theindication of the selection, determining whether a device interface ofthe second user is active; based on the device interface of the seconduser being active, generating a real-time contact request page thatincludes a contact request, a unique identifier of the first user, andinformation about the item; and transmitting, to a device of the seconduser, the real-time contact request page.
 20. The non-transitorymachine-readable medium of claim 19, wherein the operations furthercomprise: causing presentation of a setup page to the second user; andreceiving one or more preferences or conditions, via the setup page,that indicate when the real-time contact option can be included on theview item web page.